<Project Name>
Problem Resolution Plan
Version <1.0>
[Note: The following template is provided for use with the Rational Unified Process. Text enclosed in square brackets and displayed in blue italics (style=InfoBlue) is included to provide guidance to the author and should be deleted before publishing the document. A paragraph entered following this style will automatically be set to normal (style=Body Text).]
Revision History
|
Date |
Version |
Description |
Author |
|
<dd/mmm/yy> |
<x.x> |
<details> |
<name> |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Table of Contents
1.3áááá Definitions, Acronyms and Abbreviations
2.áááááá Problem Resolution Tasks
3.áááááá Organization and Responsibilities
Problem Resolution Plan
[The introduction of the Problem Resolution Plan should provide an overview of the entire document. It should include the purpose, scope, definitions, acronyms, abbreviations, references, and overview of this Problem Resolution Plan.]
[Specify the purpose of this Problem Resolution Plan.]
[A brief description of the scope of this Problem Resolution Plan; what Project(s) it is associated with and anything else that is affected or influenced by this document.]
[This subsection should provide the definitions of all terms, acronyms, and abbreviations required to properly interpret the Problem Resolution Plan. This information may be provided by reference to the project Glossary.]
[This subsection should provide a complete list of all documents referenced elsewhere in the Problem Resolution Plan.á Each document should be identified by title, report number (if applicable), date, and publishing organization.á Specify the sources from which the references can be obtained. This information may be provided by reference to an appendix or to another document.]
[This subsection should describe what the rest of the Problem Resolution Plan contains and explain how the document is organized.]
[A brief description of the Problem Resolution tasks to be performed during the project. In this section you should describe the following:
òááááá the procedure the project team will follow for reporting problems
òááááá the procedure to be used for analyzing problems
òááááá the procedure to be followed to implement appropriate corrective actions
Where these procedures differ for different categories of problems (product, project, and process, see Activity: Develop Problem Resolution Plan), describe the procedure for each under a separate sub-section.]
[List the specific groups or individuals to be involved in the analysis and resolution of each category of problem and identify the tasks and responsibilities of each.]
[List the tools and/or techniques that will be used to store problem information, analyze problems, and track the status of problems.]
[Identify problem categories and where they are stored and tracked, for example:
òááááááá Product and process problems (defects) may be stored and tracked in a Change Tracking System.
òááááááá Project problems (issues) may be tracked in an issues list, which is a component of the Status Assessment.
òááááááá Process problems (non-conformances) may be recorded in an audit report and then tracked in a Change Tracking System (as a kind of Change Request).
òááááááá Review anomalies will be recorded in the Review Record and tracked from there; if the scope of the problem requires it, a Change Request may be raised.]